Operator alertness monitor

ABSTRACT

In one example embodiment, an operator alertness monitoring system may include a proximate condition monitor that is configured to issue an alert to direct an operator&#39;s attention to a detected hazardous condition, and an operator alertness monitor that is configured to detect the operator&#39;s physical reaction to the issued alert and instruct the proximate condition monitor to respond to the operator&#39;s detected physical reaction to the issued alert.

CROSS-REFERENCE TO RELATED APPLICATION

The present application is a continuation application under 35 U.S.C. §120 of U.S. application Ser. No. 14/372,104 filed on Jul. 14, 2014,which is a U.S. National Stage filing under 35 U.S.C. § 371 ofInternational Application No. PCT/US13/66910, filed on Oct. 25, 2013.The disclosures of U.S. patent application Ser. No. 14/372,104 andInternational Application No. PCT/US13/66910 are hereby incorporated byreference in their entireties.

TECHNICAL FIELD

The embodiments described herein pertain generally to providing a highlevel of alertness for an operator of a monitored system.

BACKGROUND

Unless otherwise indicated herein, the approaches described in thissection are not prior art to the claims in this application and are notadmitted to be prior art by inclusion in this section.

Automated controls continue to be integrated into systems that havetraditionally been entrusted to human operator controls. For example,long distance flights are being entrusted to auto-pilots on anincreasing scale; operation of building maintenance systems, e.g.,climate control, is being entrusted more to automated control systems;and even the task of parallel parking of some current high-endautomobile models is being surrendered to an automated system.

SUMMARY

In one example embodiment, an operator alertness monitoring systemincludes a proximate condition monitor that is configured to issue analert to direct an operator's attention to a detected hazardouscondition, and an operator alertness monitor that is configured todetect the operator's physical reaction to the issued alert and instructthe proximate condition monitor to respond to the operator's detectedphysical reaction to the issued alert.

In another example embodiment, a method to provide driver safety, undercontrol of a processor-enabled monitoring system, includes a processorpositioning a thermal-sensing device to monitor a driver's bodytemperature, monitoring driving conditions, issuing an alert in responseto determining that the monitored driving conditions include apredefined hazard, detecting an increase in a driver's body temperaturewithin a predetermined amount of time after the alert has been issued,and issuing a reinforced alert.

In yet another example embodiment, a non-transitory computer-readablemedium may store executable-instructions that, when executed, cause oneor more processors to perform operations including: monitoring real-timephysiological data for the operator, relative to pre-storedphysiological data for the operator; monitoring operating conditions;detecting an above-threshold increase in the monitored real-timephysiological data for the operator within passage of a predeterminedamount of time when the monitored operating conditions indicate anoperating hazard; and amplifying an existing alert to the operator.

The foregoing summary is illustrative only and is not intended to be inany way limiting. In addition to the illustrative aspects, embodiments,and features described above, further aspects, embodiments, and featureswill become apparent by reference to the drawings and the followingdetailed description.

BRIEF DESCRIPTION OF THE DRAWINGS

In the detailed description that follows, embodiments are described asillustrations only since various changes and modifications will becomeapparent to those skilled in the art from the following detaileddescription. The use of the same reference numbers in different figuresindicates similar or identical items.

FIG. 1 shows an example configuration of a system in which an operatoralertness monitor may be implemented, arranged in accordance with atleast some embodiments described herein;

FIG. 2 shows an example configuration of an operator alertness monitor,arranged in accordance with at least some embodiments described herein;

FIG. 3 shows an example processing flow of operations executed by anoperator alertness monitor, arranged in accordance with at least someembodiments described herein; and

FIG. 4 shows a block diagram illustrating an example computing device bywhich various example solutions described herein may be implemented,arranged in accordance with at least some embodiments described herein.

DETAILED DESCRIPTION

In the following detailed description, reference is made to theaccompanying drawings, which form a part of the description. In thedrawings, similar symbols typically identify similar components, unlesscontext dictates otherwise. Furthermore, unless otherwise noted, thedescription of each successive drawing may reference features from oneor more of the previous drawings to provide clearer context and a moresubstantive explanation of the current example embodiment. Still, theexample embodiments described in the detailed description, drawings, andclaims are not meant to be limiting. Other embodiments may be utilized,and other changes may be made, without departing from the spirit orscope of the subject matter presented herein. It will be readilyunderstood that the aspects of the present disclosure, as generallydescribed herein and illustrated in the drawings, may be arranged,substituted, combined, separated, and designed in a wide variety ofdifferent configurations, all of which are explicitly contemplatedherein.

FIG. 1 shows an example configuration of a system 100 in which anoperator alertness monitor may be implemented, arranged in accordancewith at least some embodiments described herein. As depicted, a user 105may be a subject of system 100 that includes, at least, a proximatecondition monitor 110, an operator warning device 115, an operatoralertness monitor 120, and a biometric sensor 125. Proximate conditionmonitor 110, operator warning device 115, operator alertness monitor120, and biometric sensor 125 may, respectively, be implemented as ahardware device, as software, as firmware, or any combination thereof.Additionally, various implementations for monitoring operator alertnessmay contemplate any one or more of proximate condition monitor 110,operator alertness monitor 120, biometric sensor 125, operator warningdevice 115, or even user 105 being disposed external to system 100,without departing from the scope of the embodiments described herein.

System 100 may refer to, as non-limiting examples, a vehicle, astructure, an airplane, a datacenter, etc., in part or in its entirety,that may implement user operation and/or control even on a limitedbasis. Thus, system 100 may include automated components that mayoperate free of user intervention or involvement, at least on a limitedbasis. Non-limiting examples of such automated components may includeauto-steering, or components configured to monitor an environmentsurrounding system 100 or monitor operational performance ofsub-systems. In an automobile or a vehicle, non-limiting examples ofsuch sub-systems may include engines, brakes, climate control, parkingassistance, lane departure, blind-spot monitoring, etc. In a building orstructure, non-limiting examples of such sub-systems may include climatecontrol, building security, fire alarm, etc. In an airplane,non-limiting examples of such sub-systems may include auto-pilot,engines, brakes, landing gear, air pressure, climate control, etc. In adatacenter, non-limiting examples of such sub-systems may includeclimate control, device temperature sensor, etc. Accordingly, theaforementioned operation and/or control may include trouble-shooting orsafety monitoring.

A non-limiting example of system 100 may include, in part or in whole,an operator alertness monitoring system that includes a proximatecondition monitor that is configured to issue an alert to direct anoperator's attention to a detected hazardous condition, and an operatoralertness monitor that is configured to detect the operator'sphysiological reaction to the issued alert and instruct the proximatecondition monitor to respond to the operator's detected physiologicalreaction to the issued alert.

User 105 may refer to a person who exercises any level of operationalcontrol, trouble-shooting responsibilities, and/or safety monitoringover one or more of the aforementioned automated components of system100.

Proximate condition monitor 110 may refer to a component or module thatmay be configured, designed, and/or programmed to monitor a surroundingenvironment of system 100. For example, if system 100 is implemented asan automobile or vehicle, proximate condition monitor 110 may beconfigured, designed, and/or programmed to detect the presence ofdriving obstacles or driving hazards that may come within a thresholddistance of system 100. The threshold distance may be a static distance,e.g., three (3) feet, a set of tiered distances that invoke differentlevels of warnings, or a set of dynamically determined distances thatare based on a velocity and acceleration of the automobile or vehicle.Non-limiting examples of proximate condition monitor 110 may include amotion sensor, digital video recorder, sonar device, etc.

Alternative embodiments of proximate condition monitor 110 may beimplemented, respectively, to monitor and detect existing or potentiallydangerous or hazardous conditions relative to system 100; to monitorexternal environmental conditions, e.g., precipitation, road conditions,winds, extreme temperatures, etc.; to monitor various internaloperational components (e.g., mechanical, hardware, and software)relative to system 100; and/or to monitor other conditions that mayotherwise affect the performance of system 100 and/or the safety of user105 or any other person in or near system 100 during operation thereof.

Operator warning device 115 may refer to a device that may beconfigured, designed, and/or programmed to provide a visual and/or audiowarning or stimulus subsequent to proximate condition monitor 110determining the existence of one or more conditions that may affect theperformance of system 100 and/or the safety of user 105 or any otherperson in or near system 100 during operation thereof.

Non-limiting examples of such visual and/or audio warning produced byoperator warning device 115 may include one or more of: an illuminatedicon, e.g., battery, on a dashboard of an automobile or vehicle; atextual display, e.g., “close object,” on a dashboard or head-up displayof an automobile or vehicle; a prerecorded audio warning to advise of apotential or existing dangerous or hazardous condition relative tosystem 100; internal lights of system 100 being turned on.

Operator alertness monitor 120 may refer to a component or module thatmay be configured, designed, and/or programmed to monitor one or morephysiological responses by user 105 in response to the visual and/oraudio warning or stimulus subsequent to proximate condition monitor 110determining the existence of a potential or existing dangerous orhazardous condition relative to system 100. That is, operator alertnessmonitor 120 may be configured, designed, and/or programmed to monitorone or more physiological responses by user 105 within a predeterminedamount of time after one or more visual and/or audio warnings has beenproduced by operator warning device 150. Non-limiting exampleembodiments of operator alertness monitor 120 may include a database tostore a pre-recorded physiological profile of user 105 including, butnot limited to, a resting heart rate, a resting body temperature, etc.;and/or standardized or threshold values thereof. Alternatively, or inaddition, operator alertness monitor 120 may be configured to receive astorage device, e.g., a flash drive, on which the aforementionedphysiological profile for user 105 may be stored, for utilization inproviding operator alertness. Alternatively, or in addition, operatoralertness monitor 120 may further be wirelessly connected to a serviceprovider, e.g., OnStar®, to which user 105 and/or system 100 may beregistered, at which the aforementioned physiological profile for user105 may be stored.

Biometric sensor 125 may refer to a device that may be configured,designed, and/or programmed to measure physiological responses for user105 at any given time. Non-limiting examples of the physiologicalresponses measured by biometric sensor 125 may include: a thermalimaging camera configured to monitor and measure the skin temperaturefor user 105, e.g., facial temperature; a thermal monitor that may beembedded in, e.g., a seat, steering wheel, etc., of system 100, andconfigured to monitor and measure the body temperature for user 105; apulse monitor that may be embedded in, e.g., a seat, steering wheel,etc., of system 100, and configured to monitor and measure the pulserate for user 105; etc. In accordance with various example embodiments,biometric sensor 125 may be positioned to obtain virtually instantaneousreadings of physiological parameters for user 105 at a given moment.Thus, for example, as a thermal imaging camera, biometric sensor 125 maybe automatically or manually positioned to focus on a designated portionof the anatomy, e.g., the face, of user 105 during a beginning stage ofuse.

In non-limiting example embodiments, biometric sensor 125 may bepositioned or physically integrated with operator alertness monitor 120,connected to operator alertness monitor 120 via a wired connection, orconnected to operator alertness monitor 120 via a wired connection suchas a short-range communication protocol.

Further, depending upon an implementation of system 100, which mayinclude, as non-limiting examples, a vehicle, structure, airplane,datacenter, etc., in part or in its entirety, biometric sensor 125 maybe disposed and positioned appropriate in an operator's control panel,control console, cockpit, etc.

Accordingly, operator alertness monitor 120, in combination withbiometric sensor 125, may operate to continuously or periodicallymonitor one or more physiological responses of user 105 within apredetermined amount of time after one or more visual and/or audiowarnings has been produced by operator warning device 115. By way ofexample, subsequent to a visual and/or audio warning being produced byoperator warning device 115, if the body/skin temperature and/or pulserate of user 105 is measured or detected as increasing by apredetermined amount within a threshold amount of time, operatoralertness monitor 120 may determine that user 105 is indeed sufficientlyaware of the detected potential or existing dangerous or hazardouscondition relative to system 100 in order to take corrective action. Thedetermination may be predicated upon an assumption that an operator whois made aware of a potentially dangerous or hazardous condition mayincur a surge of adrenaline that results in a discernible increase inbody/skin temperature and/or pulse rate.

However, if the body/skin temperature and/or pulse rate of user 105 ismeasured or detected as remaining beneath the aforementionedpredetermined amount thereof, operator alertness monitor 120 mayoperatively prompt operator warning device 115 to produce a heightenedvisual and/or audio warning or stimulus to alert user 105 of theexisting or potential dangerous or hazardous condition relative tosystem 100. Non-limiting examples of the heightened warning or stimulusmay include a brighter version of the previously produced visual warningand/or a louder version of the previously produced audio warning.Alternatively, or in addition, operator warning device may be furtherconfigured, designed, and/or programmed to implement corrective actionsuch as reducing a current velocity of system 100, taking evasiveaction, turning system 100 away from a detected obstacle, shuttingsystem 100 down in part or in whole, etc. Of course, such correctiveaction is largely dependent upon an implementation of system 100, e.g.,as a vehicle, structure, airplane, datacenter, etc.

FIG. 2 shows an example configuration of operator alertness monitor 120,arranged in accordance with at least some embodiments described herein.As depicted, operator alertness monitor 120 may include, at least, adevice alert monitor 205, a timer 210, an operator awareness detector215, a physiological parameter database 220, and an operator warningdevice interface 230. Device alert monitor 205, timer 210, operatorawareness detector 215, physiological parameter database 220, andoperator warning device interface 225 may, respectively, be implementedas a hardware device, as software, as firmware, or any combinationthereof. Additionally, various implementations for monitoring operatoralertness may contemplate physiological parameter database 220 beingdisposed external to operator alertness monitor 120 or even system 100,without departing from the scope of the embodiments described herein.

Device alert monitor 205 may refer to a component or module that may beconfigured, designed, and/or programmed to monitor and detect whetheroperator warning device 115 has produced a visual and/or audio warningor stimulus subsequent to proximate condition monitor 110 determiningthe existence of one or more conditions that may affect the performanceof system 100 and/or the safety of user 105 or any other person in ornear system 100 during operation thereof. Alternatively, or in addition,device alert monitor 205 may be configured, designed, and/or programmedto monitor proximate condition monitor 110 to detect whether proximatecondition monitor 110 has determined the existence of one or more suchexisting or potential dangerous or hazardous conditions, relative tosystem 100.

Timer 210 may refer to a timer that may be communicatively coupled todevice alert monitor 205 further configured and/or programmed tocommence marking time at a substantially same instant that device alertmonitor 205 has detected operator warning device 115 producing a visualand/or audio warning or stimulus subsequent to proximate conditionmonitor 110 determining the existence of one or more conditions that mayaffect the performance of system 100 and/or the safety of user 105 orany other person in or near system 100 during operation thereof.Alternatively, or in addition, timer 210 may be communicatively coupledto proximate condition monitor 110 and/or operator warning device 115 tocommence marking time at a substantially same instant that an existingor potential dangerous or hazardous condition has been detected relativeto system 100.

Operator awareness detector 215 may refer to a component or module thatis communicatively coupled to biometric sensor 125 and furtherconfigured, designed, and/or programmed to monitor physiologicalparameters, including but not limited to body/skin temperature and/orpulse rate, for user 105. Thus, when device alert monitor 205 hasdetected that operator warning device 115 has produced a visual and/oraudio warning or stimulus subsequent to proximate condition monitor 110determining an existing or potential dangerous or hazardous conditionrelative to system 100, operator awareness detector 215 may furthermeasure any increase in the physiological parameters measured bybiometric sensor 125. Operator awareness detector 215 may compare anymeasured increase in the measured physiological parameters to apredetermined threshold, e.g., 2° F., 10 beats/minute, that have beenpre-established as being indicative of a physiological response to anexternal stimulus or emergency, such as a surge of adrenaline thatresults in a discernible increase in body/skin temperature and/or pulserate. Accordingly, within a predetermined amount of time, as monitoredby timer 210, operator awareness detector 215 may determine whether ornot user 105 has heeded a visual and/or audio warning produced byoperator warning device 115 and is aware of the existing or potentialdangerous or hazardous condition relative to system 100.

Operator awareness detector 215 may be further configured, designed,and/or programmed to record the aforementioned physiological parametersfor user 105 within a predetermined amount of time, as marked by timer210. The predetermined amount of time may vary in accordance with thedetected existing or potential dangerous or hazardous condition relativeto system 100. As non-limiting examples, if an oncoming vehicle isdetected, the predetermined amount of time may be less than one second;if rumble strips beneath a corresponding vehicle's wheels are detected,the predetermined amount may be three (3) seconds or less; or if anoverheating engine is detected, the predetermined amount of time may be15 seconds or less. The preceding values are provided as examples onlyto demonstrate the non-uniformity and dynamic nature of theaforementioned predetermined amount of time, and are not intended to belimiting to any of the example embodiments described herein.

Physiological parameter database 220 may refer to a local database orcommunicative connection thereto or a receptacle for an external devicein which may be stored at least a pre-recorded physiological profile foruser 105.

In accordance with the various embodiments described above, operatorawareness detector 215 may compare any measured increase in the measuredphysiological parameters of user 105 to a pre-recorded physiologicalprofile of user 105 including, but not limited to, a resting heart rate,a resting body temperature, etc.; and/or standardized or thresholdvalues thereof. Such pre-recorded physiological profile and/orstandardized or threshold values may be stored, alternatively or inaddition, on an external device, e.g., flash drive, received by operatoralertness monitor 120; or hosted by a remote server or third-partyservice provider, e.g., OnStar®, to which user 105 and/or system 100 maybe registered.

Operator warning device interface 225 may refer to a component or modulethat is communicatively coupled to operator warning device 115 andfurther configured, designed, and/or programmed to transmit anindication of the physiological parameters for user 105, as monitoredand measured within a predetermined amount of time corresponding to thedetected existing or potential dangerous or hazardous condition relativeto system 100, as marked by timer 210. Thus, if the physiologicalparameters for user 105 monitored and measured within the predeterminedamount of time indicate that user 105 is sufficiently aware of thedetected existing or potential dangerous or hazardous condition relativeto system 100 in order to take corrective action, then operator warningdevice interface 225 may transmit an instruction for operator warningdevice 115 to turn off an activated visual and/or audio warning.

Further, if the physiological parameters for user 105 monitored andmeasured within the predetermined amount of time indicate that user 105is not sufficiently aware of the detected existing or potentialdangerous or hazardous condition relative to system 100 in order to takecorrective action, then operator warning device interface 225 maytransmit an instruction for operator warning device 115 to produce aheightened visual and/or audio warning or stimulus to alert user 105 ofthe existing or potential dangerous or hazardous condition relative tosystem 100. As described above, non-limiting examples of the heightenedwarning or stimulus may include a brighter version of the previouslyproduced visual warning and/or a louder version of the previouslyproduced audio warning. Alternatively, or in addition, operator warningdevice interface 225 may transmit an instruction for operator warningdevice to activate a corrective action such as reducing a currentvelocity of system 100, taking evasive action, turning system 100 awayfrom a detected obstacle, shutting system 100 down in part or in whole,etc. Of course, such corrective action is largely dependent upon animplementation of system 100, e.g., as a vehicle, structure, airplane,datacenter, etc. In accordance with further alternative embodiments,operator warning device 115 may already be programmed to activate one ormore corrective actions, without instruction or prompting from operatorwarning device interface 225.

FIG. 3 shows an example processing flow 300 of operations executed by anoperator alertness monitor, arranged in accordance with at least someembodiments described herein. Processing flow 300 may be implemented bythe depicted embodiment of datacenter system configuration 100 orvarious permutations thereof. Processing flow 300 may include one ormore operations, actions, or functions depicted by one or more blocks305, 310, 315, 320, 325, and 330. Although illustrated as discreteblocks, various blocks may be divided into additional blocks, combinedinto fewer blocks, or eliminated, depending on the desiredimplementation. Further, blocks 305 and 310 are depicted as beingattributed to operator warning device 115 and blocks 315, 320, 325, and330 are depicted as being attributed to operator awareness monitor 120.Such depiction is consistent with some of the example embodimentsdescribed with regard to FIGS. 1 and 2. However, alternatively,embodiments described herein may contemplate respective blocks ofprocessing flow 300 being attributed to different features of system100. Processing may begin at block 305.

Block 305 (Detect Adverse Condition) may refer to proximate conditionmonitor 110 detecting one or more existing or potential dangerous orhazardous conditions that may affect the performance of system 100and/or the safety of user 105 or any other person in or near system 100during operation thereof.

Block 310 (Alert Operator) may refer to operator warning device 115providing or activating a visual and/or audio warning or stimulussubsequent to proximate condition monitor 110 detecting the one or moreexisting or potential dangerous or hazardous conditions relative tosystem 100. Non-limiting examples of such visual and/or audio warningproduced by operator warning device 115 may include one or more of: anilluminated icon, e.g., battery, on a dashboard of an automobile orvehicle; a textual display, e.g., “close object,” on a dashboard orhead-up display of an automobile or vehicle; a prerecorded audio warningto advise of a potential or existing dangerous or hazardous conditionrelative to system 100; internal lights of system 100 being turned on.Block 310 may be followed by decision block 315.

Block 315 (Monitor Operator) may refer to biometric sensor 125 andoperator awareness detector 215, serially or in combination, measuringand monitoring physiological parameters for user 105 upon activation oftimer 210, which may occur at the time operator warning device providesor activates a visual and/or warning or stimulus or, alternatively, atthe time proximate condition monitor 110 detects one or more existing orpotential dangerous or hazardous conditions relative to system 100.Block 315 may be followed by decision block 320.

Decision block 320 (Operator Alert Within Threshold Time?) may refer tooperator awareness detector 215 determining whether biometric sensor 125and operator awareness detector 215, serially or in combination, havedetected a sufficient increase in one or more of the monitored andmeasured physiological parameters for user 105 within the predeterminedamount of time corresponding to the detected adverse condition. That is,decision block 320 may refer to operator awareness detector 215determining whether or not user 105 has heeded a visual and/or audiowarning produced by operator warning device 115 and is aware of theexisting or potential dangerous or hazardous condition relative tosystem 100. Upon a positive determination, decision block 320 may befollowed by block 325; but upon a negative determination, decision block320 may be followed by block 330.

Block 325 (End) may refer to operator warning device interface 225transmitting an instruction for operator warning device 115 to turn offan activated visual and/or audio warning when the physiologicalparameters for user 105 monitored and measured within the predeterminedamount of time indicate that user 105 is sufficiently aware of thedetected existing or potential dangerous or hazardous condition relativeto system 100 in order to take corrective action.

Block 330 (Alert Operator) may refer to operator warning deviceinterface 225 transmitting an instruction for operator warning device115 to produce a heightened visual and/or audio warning or stimulus toalert user 105 of the existing or potential dangerous or hazardouscondition relative to system 100.

Accordingly, processing flow 300, as implemented by various modules orcomponents of system 100, may provide an increased level of operatoralertness.

FIG. 4 shows a block diagram illustrating an example computing device bywhich various example solutions described herein may be implemented,arranged in accordance with at least some embodiments described herein.

In a very basic configuration 402, computing device 400 typicallyincludes one or more processors 404 and a system memory 406. A memorybus 408 may be used for communicating between processor 404 and systemmemory 406.

Depending on the desired configuration, processor 404 may be of any typeincluding but not limited to a microprocessor (μP), a microcontroller(μC), a digital signal processor (DSP), or any combination thereof.Processor 404 may include one or more levels of caching, such as a levelone cache 410 and a level two cache 412, a processor core 414, andregisters 416. An example processor core 414 may include an arithmeticlogic unit (ALU), a floating point unit (FPU), a digital signalprocessing core (DSP Core), or any combination thereof. An examplememory controller 418 may also be used with processor 404, or in someimplementations, memory controller 418 may be an internal part ofprocessor 404.

Depending on the desired configuration, system memory 406 may be of anytype including but not limited to volatile memory (such as RAM),non-volatile memory (such as ROM, flash memory, etc.) or any combinationthereof. System memory 406 may include an operating system 420, one ormore applications 422, and program data 424. Application 422 may includeone or more monitoring algorithms 426 that may be arranged to performthe functions as described herein including those described with respectto processing flow 300 of FIG. 3. Program data 424 may includephysiological parameter profile data 428 that may be utilized for thecomparisons performed by the various monitoring algorithms 426 asdescribed herein. Physiological parameter profile data 428 may includeprofile data for user 105 or for an anticipated generic or default userof system 100. In some embodiments, application 422 may be arranged tooperate with program data 424 on operating system 420 such thatimplementations of monitoring operator alertness may be provided asdescribed herein. This described basic configuration 402 is illustratedin FIG. 4 by those components within the inner dashed line.

Computing device 400 may have additional features or functionality, andadditional interfaces to facilitate communications between basicconfiguration 402 and any required devices and interfaces. For example,a bus/interface controller 430 may be used to facilitate communicationsbetween basic configuration 402 and one or more data storage devices 432via a storage interface bus 434. Data storage devices 432 may beremovable storage devices 436, non-removable storage devices 438, or acombination thereof. Examples of removable storage and non-removablestorage devices include magnetic disk devices such as flexible diskdrives and hard-disk drives (HDD), optical disk drives such as compactdisk (CD) drives or digital versatile disk (DVD) drives, solid statedrives (SSD), and tape drives to name a few. Example computer storagemedia may include volatile and nonvolatile, removable and non-removablemedia implemented in any method or technology for storage ofinformation, such as computer readable instructions, data structures,program modules, or other data.

System memory 406, removable storage devices 436 and non-removablestorage devices 438 are examples of computer storage media. Computerstorage media includes, but is not limited to, RAM, ROM, EEPROM, flashmemory or other memory technology, CD-ROM, digital versatile disks (DVD)or other optical storage, magnetic cassettes, magnetic tape, magneticdisk storage or other magnetic storage devices, or any other mediumwhich may be used to store the desired information and which may beaccessed by computing device 400. Any such computer storage media may bepart of computing device 400.

Computing device 400 may also include an interface bus 440 forfacilitating communication from various interface devices (e.g., outputdevices 442, peripheral interfaces 444, and communication devices 446)to basic configuration 402 via bus/interface controller 430. Exampleoutput devices 442 include a graphics processing unit 448 and an audioprocessing unit 450, which may be configured to communicate to variousexternal devices such as a display or speakers via one or more A/V ports452. Example peripheral interfaces 544 include a serial interfacecontroller 454 or a parallel interface controller 456, which may beconfigured to communicate with external devices such as input devices(e.g., keyboard, mouse, pen, voice input device, touch input device,etc.) or other peripheral devices (e.g., printer, scanner, etc.) via oneor more I/O ports 458. An example communication device 446 includes anetwork controller 460, which may be arranged to facilitatecommunications with one or more other computing devices 462 over anetwork communication link via one or more communication ports 464.

The network communication link may be one example of a communicationmedia. Communication media may typically be embodied by computerreadable instructions, data structures, program modules, or other datain a modulated data signal, such as a carrier wave or other transportmechanism, and may include any information delivery media. A modulateddata signal may be a signal that has one or more of its characteristicsset or changed in such a manner as to encode information in the signal.By way of example, and not limitation, communication media may includewired media such as a wired network or direct-wired connection, andwireless media such as acoustic, radio frequency (RF), microwave,infrared (IR) and other wireless media. The term computer readable mediaas used herein may include both storage media and communication media.

Computing device 400 may be implemented as a portion of a small-formfactor portable (or mobile) electronic device such as a cell phone, apersonal data assistant (PDA), a personal media player device, awireless web-watch device, a personal headset device, an applicationspecific device, or a hybrid device that include any of the abovefunctions. Computing device 400 may also be implemented as a server or apersonal computer including both laptop computer and non-laptop computerconfigurations.

There is little distinction left between hardware and softwareimplementations of aspects of systems; the use of hardware or softwareis generally (but not always, in that in certain contexts the choicebetween hardware and software can become significant) a design choicerepresenting cost vs. efficiency tradeoffs. There are various vehiclesby which processes and/or systems and/or other technologies describedherein may be implemented, e.g., hardware, software, and/or firmware,and that the preferred vehicle may vary with the context in which theprocesses and/or systems and/or other technologies are deployed. Forexample, if an implementer determines that speed and accuracy areparamount, the implementer may opt for a mainly hardware and/or firmwarevehicle; if flexibility is paramount, the implementer may opt for amainly software implementation; or, yet again alternatively, theimplementer may opt for some combination of hardware, software, and/orfirmware.

The foregoing detailed description has set forth various embodiments ofthe devices and/or processes for system configuration 100 via the use ofblock diagrams, flowcharts, and/or examples. Insofar as such blockdiagrams, flowcharts, and/or examples contain one or more functionsand/or operations, it will be understood by those within the art thateach function and/or operation within such block diagrams, flowcharts,or examples can be implemented, individually and/or collectively, by awide range of hardware, software, firmware, or virtually any combinationthereof. In one embodiment, several portions of the subject matterdescribed herein may be implemented via Application Specific IntegratedCircuits (ASICs), Field Programmable Gate Arrays (FPGAs), digital signalprocessors (DSPs), or other integrated formats. However, those skilledin the art will recognize that some aspects of the embodiments disclosedherein, in whole or in part, can be equivalently implemented inintegrated circuits, as one or more computer programs running on one ormore computers, e.g., as one or more programs running on one or morecomputer systems, as one or more programs running on one or moreprocessors, e.g., as one or more programs running on one or moremicroprocessors, as firmware, or as virtually any combination thereof,and that designing the circuitry and/or writing the code for thesoftware and/or firmware would be well within the skill of one of skillin the art in light of this disclosure. In addition, those skilled inthe art will appreciate that the mechanisms of the subject matterdescribed herein are capable of being distributed as a program productin a variety of forms, and that an illustrative embodiment of thesubject matter described herein applies regardless of the particulartype of signal bearing medium used to actually carry out thedistribution. Examples of a signal bearing medium include, but are notlimited to, the following: a recordable type medium such as a floppydisk, a hard disk drive (HDD), a compact disk (CD), a digital versatiledisk (DVD), a digital tape, a computer memory, etc.; and a transmissiontype medium such as a digital and/or an analog communication medium,e.g., a fiber optic cable, a waveguide, a wired communication link, awireless communication link, etc.

Those skilled in the art will recognize that it is common within the artto describe devices and/or processes in the fashion set forth herein,and thereafter use engineering practices to integrate such describeddevices and/or processes into data processing systems. That is, at leasta portion of the devices and/or processes described herein can beintegrated into a data processing system via a reasonable amount ofexperimentation. Those having skill in the art will recognize that atypical data processing system generally includes one or more of asystem unit housing, a video display device, a memory such as volatileand non-volatile memory, processors such as microprocessors and digitalsignal processors, computational entities such as operating systems,drivers, graphical user interfaces, and applications programs, one ormore interaction devices, such as a touch pad or screen, and/or controlsystems including feedback loops and control motors, e.g., feedback forsensing position and/or velocity; control motors for moving and/oradjusting components and/or quantities. A typical data processing systemmay be implemented utilizing any suitable commercially availablecomponents, such as those typically found in datacomputing/communication and/or network computing/communication systems.

The herein described subject matter sometimes illustrates differentcomponents contained within, or connected with, different othercomponents. It is to be understood that such depicted architectures aremerely examples, and that in fact many other architectures can beimplemented which achieve the same functionality. In a conceptual sense,any arrangement of components to achieve the same functionality iseffectively “associated” such that the desired functionality isachieved. Hence, any two components herein combined to achieve aparticular functionality can be seen as “associated with” each othersuch that the desired functionality is achieved, irrespective ofarchitectures or intermedial components. Likewise, any two components soassociated can also be viewed as being “operably connected”, or“operably coupled”, to each other to achieve the desired functionality,and any two components capable of being so associated can also be viewedas being “operably couplable”, to each other to achieve the desiredfunctionality. Specific examples of operably couplable include but arenot limited to physically mateable and/or physically interactingcomponents and/or wirelessly interactable and/or wirelessly interactingcomponents and/or logically interacting and/or logically interactablecomponents.

Lastly, with respect to the use of substantially any plural and/orsingular terms herein, those having skill in the art can translate fromthe plural to the singular and/or from the singular to the plural as isappropriate to the context and/or application. The varioussingular/plural permutations may be expressly set forth herein for sakeof clarity.

It will be understood by those within the art that, in general, termsused herein, and especially in the appended claims, e.g., bodies of theappended claims, are generally intended as “open” terms, e.g., the term“including” should be interpreted as “including but not limited to,” theterm “having” should be interpreted as “having at least,” the term“includes” should be interpreted as “includes but is not limited to,”etc. It will be further understood by those within the art that if aspecific number of an introduced claim recitation is intended, such anintent will be explicitly recited in the claim, and in the absence ofsuch recitation, no such intent is present. For example, as an aid tounderstanding, the following appended claims may contain usage of theintroductory phrases “at least one” and “one or more” to introduce claimrecitations. However, the use of such phrases should not be construed toimply that the introduction of a claim recitation by the indefinitearticles “a” or “an” limits any particular claim containing suchintroduced claim recitation to embodiments containing only one suchrecitation, even when the same claim includes the introductory phrases“one or more” or “at least one” and indefinite articles such as “a” or“an,” e.g., “a” and/or “an” should be interpreted to mean “at least one”or “one or more;” the same holds true for the use of definite articlesused to introduce claim recitations. In addition, even if a specificnumber of an introduced claim recitation is explicitly recited, thoseskilled in the art will recognize that such recitation should beinterpreted to mean at least the recited number, e.g., the barerecitation of “two recitations,” without other modifiers, means at leasttwo recitations, or two or more recitations. Furthermore, in thoseinstances where a convention analogous to “at least one of A, B, and C,etc.” is used, in general, such a construction is intended in the senseone having skill in the art would understand the convention, e.g., “asystem having at least one of A, B, and C” would include but not belimited to systems that have A alone, B alone, C alone, A and Btogether, A and C together, B and C together, and/or A, B, and Ctogether, etc. In those instances where a convention analogous to “atleast one of A, B, or C, etc.” is used, in general, such a constructionis intended in the sense one having skill in the art would understandthe convention, e.g., “a system having at least one of A, B, or C” wouldinclude but not be limited to systems that have A alone, B alone, Calone, A and B together, A and C together, B and C together, and/or A,B, and C together, etc. It will be further understood by those withinthe art that virtually any disjunctive word and/or phrase presenting twoor more alternative terms, whether in the description, claims, ordrawings, should be understood to contemplate the possibilities ofincluding one of the terms, either of the terms, or both terms. Forexample, the phrase “A or B” will be understood to include thepossibilities of “A” or “B” or “A and B.”

From the foregoing, it will be appreciated that various embodiments ofthe present disclosure have been described herein for purposes ofillustration, and that various modifications may be made withoutdeparting from the scope and spirit of the present disclosure.Accordingly, the various embodiments disclosed herein are not intendedto be limiting, with the true scope and spirit being indicated by thefollowing claims.

The invention claimed is:
 1. A hazard management system comprising: a proximate condition monitor configured to detect a hazardous condition, wherein the detected hazardous condition comprises one or more of an external obstacle and a localized technical failure; an operator alertness monitor coupled to the proximate condition monitor and configured to monitor physiological reaction of an operator to the detected hazardous condition, within a particular time period, to determine whether the operator is aware of the detected hazardous condition, wherein the particular time period varies in accordance with a type of the detected hazardous condition; and a warning device coupled to the proximate condition monitor and the operator alertness monitor, wherein the warning device is configured to implement a corrective action to manage the detected hazardous condition, in response to a determination that the operator is unaware of the detected hazardous condition.
 2. The hazard management system of claim 1, wherein the implementation of the corrective action includes one or more of a reduction of a current velocity of an automobile, an evasive action, a diversion of a monitored system away from the detected hazardous condition, and a power off of the automobile.
 3. The hazard management system of claim 1, wherein the hazardous condition comprises at least one of an approaching object and a mechanical failure.
 4. A hazard management system comprising: a proximate condition monitor configured to detect a hazardous condition associated with driving conditions, wherein the detected hazardous condition comprises one or more of an external obstacle and a localized technical failure; an operator alertness monitor coupled to the proximate condition monitor and configured to detect an increase in a body temperature of a driver, within a particular time period, to determine whether the driver is aware of the detected hazardous condition, wherein the particular time period varies in accordance with a type of the detected hazardous condition; and a warning device coupled to the proximate condition monitor and the operator alertness monitor, wherein the warning device is configured to implement a corrective action to manage the detected hazardous condition, in response to a determination that the driver is unaware of the detected hazardous condition.
 5. The hazard management system of claim 4, wherein the implementation of the corrective action includes one or more of a reduction of a current velocity of an automobile, an evasive action, a diversion of a monitored system away from the detected hazardous condition, and a power off of the automobile.
 6. The hazard management system of claim 4, wherein: the operator alertness monitor is further configured to determine that the body temperature of the driver is below a particular body temperature to determine that the driver is unaware of the detected hazardous condition.
 7. The hazard management system of claim 4, wherein the operator alertness monitor includes a thermal imaging camera.
 8. The hazard management system of claim 4, wherein: the hazard management system is included in an automobile, and the operator alertness monitor includes a thermal imaging camera, directed at a driver's seat.
 9. The hazard management system of claim 4, wherein the operator alertness monitor includes a body temperature sensor embedded within a driver's seat.
 10. The hazard management system of claim 4, wherein the operator alertness monitor includes a thermal imaging camera that is configured to detect the increase in the body temperature of the driver, relative to a particular threshold value, within the particular time period.
 11. The hazard management system of claim 4, wherein the operator alertness monitor includes a body temperature sensor connected to a steering wheel, and wherein the body temperature sensor is configured to detect the increase in the body temperature of the driver, relative to a particular threshold value, within the particular time period.
 12. The hazard management system of claim 4, wherein the hazardous condition includes at least one of precipitation, rumble strips, a vehicle within a particular perimeter, road conditions, wind conditions, an engine malfunction, and a software malfunction.
 13. The hazard management system of claim 4, wherein the hazardous condition comprises at least one of an approaching object and a mechanical failure.
 14. A method to provide a corrective action for a hazardous condition, the method comprising: detecting the hazardous condition, wherein the detected hazardous condition comprises one or more of an external obstacle and a localized technical failure; monitoring real-time physiological parameters of an operator, responsive to the detected hazardous condition; comparing the monitored real-time physiological parameters of the operator to a pre-stored physiological profile of the operator; in response to the comparison, detecting an above-threshold increase in the monitored real-time physiological parameters of the operator within a particular time period for determining whether the operator is aware of the detected hazardous condition, wherein the particular time period varies in accordance with a type of the detected hazardous condition; and implementing the corrective action to manage the detected hazardous condition, in response to a determination that the operator is unaware of the detected hazardous condition.
 15. The method of claim 14, wherein implementing the corrective action includes one or more of reducing a current velocity of an automobile, an evasive action, diverting a monitored system away from the detected hazardous condition, and powering off the automobile.
 16. The method of claim 14, wherein issuing an alert to direct attention of the operator to the detected hazardous condition comprises generating an audible alarm.
 17. The method of claim 14, wherein the real-time physiological parameters of the operator include at least one of a body temperature, a pulse rate, and a blood pressure value.
 18. The method of claim 14, wherein the hazardous condition comprises at least one of an approaching object and a mechanical failure. 